Open topic with navigation
You are here: Restoration > Restoring an entire server to an ESX virtual server
Restoring an entire server to an ESX virtual server
Use these instructions to restore an entire server to an ESX virtual server.
- Create a virtual guest on your ESX server.
- Configure the memory and CPUs as needed.
- For the hard drives, use virtual SCSI disks and the LSI Logic SCSI controller
- Configure your virtual disks using the same configuration (size and file system type) as the original source you are restoring
- Install the operating system on the guest, making sure to match the operating system version, kernel version, kernel type, and file system as the original source you are restoring.
- Install Double-Take Availability on the guest, using a valid Double-Take Availability activation code. You can reuse the activation code that was used on your original source, while the original source is not active.
- Configure networking on the guest, making sure that it can communicate with the Double-Take Availability target which has the copy of the original source you are restoring.
- For Red Hat-based guests, reboot the guest into single user mode. For Novell-based guests, you will want to reboot to run-level 2. You cannot issue a run-level change command. You must reboot in order to pause necessary processes.
- At the grub boot menu, press any key.
- Highlight your kernel from the list.
-
For Red Hat-based guests, press a to append additional options to the command line, and then at the grub append command prompt, add the word single to the end of the command and press Enter.
- For Novell-based guests, press 2 to take the guest to run-level 2 and then manually shut down non-essential services, such as third-party applications or daemons.
- After the boot process has completed, run the following initialization scripts. For Novell-based guests, you do not need to run the network script because run-level 2 includes networking.
- /etc/init.d/network start
- /etc/init.d/DT start
- /etc/init.d/sshd start
- Make a copy of the guest's kernel mode configuration file. By default, this is /etc/modprobe.conf for Red Hat-based guests and /etc/sysconfig/kernel for Novell-based guests. Append .pre-migration to the end of the filename when performing the copy. For example, /etc/modprobe.conf will become /etc/modprobe.conf.pre-migration. This copy is required to maintain data specific to your guest that is at risk of being lost by overwriting configuration files during the restoration.
- From the Replication Console, select Tools, Restoration Wizard.
-
Review the Welcome screen and click Next to continue.
At any time while using the Restoration Wizard, click Back to return to previous screens and review your selections.
- Select the target that contains the copy of the original source that you want to restore and click Next.
- Select the original source. This option identifies to the target which data set you are trying to restore so that the appropriate replication sets can be presented to you.
- Click Next to continue.
- Select Use this replication set and specify the Server_Image replication set.
- Click Next to continue.
- A tree display appears identifying the data available for restoration. Verify the existing selection of the volumes, directories, and/or files you want to restore. Keep in mind that if you exclude volumes, folders, and/or files, it may compromise the integrity of your applications or data.
- Click Next to continue
- Select the new source server. This is the guest that you just created. Click Next to continue.
-
Select your network route to the guest, which includes the IP address and port number. Do not modify the Source Path or Target Path.
- Click Next to continue.
-
On the Restoration Options page, select the following options.
- Replicate data during the restoration connection—Disable this option. It is not required when restoring an entire server.
- Restore replication set definition to new source—Enable this option. It restores a copy of the replication set database on the target to the new source.
- Overwrite existing data during restore—Enable this option. It restores all existing files by overwriting them and writes any files that do not exist. If this option is disabled, only files that do not exist on the new source will be restored.
- Only if backup copy's date is more recent—Disable this option. It restores only those files that are newer on the target than on the new source. The entire file is overwritten with this option.
- Use Checksum comparison to send minimal blocks of data—You can enable or disable this option as desired. It specifies if you want the restoration process to use a block checksum comparison to determine which blocks are different. If this option is enabled, only those blocks (not the entire files) that are different will be restored to the new source.
- Use alternate target files for executables that may be in use—This option is enabled by default and cannot be changed in this context.
- Review your selections and click Finish to begin the restoration.
After the restoration mirror is complete, the restoration connection will automatically be disconnected and the replication set will be deleted. After the restoration replication set is deleted, you will need to perform additional post-restoration steps specific to your guest. If you restored to a Red Hat-based guest, see Configuring Red Hat-based guests after restoring. If you restored to a Novell-based guest, see Configuring Novell-based guests after restoring.